Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[COST-5032] switch to kube_persistentvolume_capacity_bytes #354

Merged
merged 3 commits into from
May 15, 2024
Merged

Conversation

maskarb
Copy link
Member

@maskarb maskarb commented May 14, 2024

  • kube_persistentvolume_capacity_bytes contains data for every PV and it's result actually matches the the value defined in the PV definition.

Copy link

codecov bot commented May 14, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 86.13%. Comparing base (2366855) to head (57d4e94).

Additional details and impacted files

Impacted file tree graph

@@           Coverage Diff           @@
##             main     #354   +/-   ##
=======================================
  Coverage   86.13%   86.13%           
=======================================
  Files          13       13           
  Lines        2171     2171           
=======================================
  Hits         1870     1870           
  Misses        220      220           
  Partials       81       81           
Flag Coverage Δ
unittests 86.13% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.


Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 2366855...57d4e94. Read the comment docs.

@maskarb maskarb merged commit 16ae929 into main May 15, 2024
10 checks passed
@maskarb maskarb deleted the cost-5032 branch May 15, 2024 18:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants